Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try to support multi-line output values for Github comment #213

Merged
merged 1 commit into from
Jun 19, 2024

Conversation

danielnaab
Copy link
Contributor

No description provided.

Copy link

Terraform Plan

tts-10x-atj-staging  Initializing the backend...
tts-10x-atj-staging  Successfully configured the backend "s3"! Terraform will automatically
                     use this backend unless the backend configuration changes.
tts-10x-atj-staging  Initializing provider plugins...
                     - Finding cloudfoundry-community/cloudfoundry versions matching "0.53.1"...
tts-10x-atj-staging  - Finding hashicorp/aws versions matching "5.54.1"...
tts-10x-atj-staging  - Installing cloudfoundry-community/cloudfoundry v0.53.1...
tts-10x-atj-staging  - Installed cloudfoundry-community/cloudfoundry v0.53.1 (self-signed, key ID C0E4EB79E9E6A23D)
tts-10x-atj-staging  - Installing hashicorp/aws v5.54.1...
tts-10x-atj-staging
tts-10x-atj-staging  - Installed hashicorp/aws v5.54.1 (signed by HashiCorp)

                     Partner and community providers are signed by their developers.
                     If you'd like to know more about provider signing, you can read about it here:
                     https://www.terraform.io/docs/cli/plugins/signing.html

                     Terraform has created a lock file .terraform.lock.hcl to record the provider
                     selections it made above. Include this file in your version control repository
                     so that Terraform can guarantee to make the same selections by default when
                     you run "terraform init" in the future.
tts-10x-atj-staging  Terraform has been successfully initialized!

                     You may now begin working with Terraform. Try running "terraform plan" to see
                     any changes that are required for your infrastructure. All Terraform commands
                     should now work.

                     If you ever set or change modules or backend configuration for Terraform,
                     rerun this command to reinitialize your working directory. If you forget, other
                     commands will detect it and remind you to do so if necessary.
tts-10x-atj-staging  - Fetching hashicorp/aws 5.54.1 for linux_amd64...
tts-10x-atj-staging  - Retrieved hashicorp/aws 5.54.1 for linux_amd64 (signed by HashiCorp)
tts-10x-atj-staging  - Fetching cloudfoundry-community/cloudfoundry 0.53.1 for linux_amd64...
tts-10x-atj-staging  - Retrieved cloudfoundry-community/cloudfoundry 0.53.1 for linux_amd64 (self-signed, key ID C0E4EB79E9E6A23D)
                     - Obtained hashicorp/aws checksums for linux_amd64; All checksums for this platform were already tracked in the lock file
                     - Obtained cloudfoundry-community/cloudfoundry checksums for linux_amd64; All checksums for this platform were already tracked in the lock file
tts-10x-atj-staging  Success! Terraform has validated the lock file and found no need for changes.
tts-10x-atj-staging  data.aws_ssm_parameter.tts-10x-atj-staging-cloudfoundry-username (tts-10x-atj-staging-cloudfoundry-username): Reading...
tts-10x-atj-staging  data.aws_ssm_parameter.tts-10x-atj-staging-cloudfoundry-password (tts-10x-atj-staging-cloudfoundry-password): Reading...
tts-10x-atj-staging  data.aws_ssm_parameter.tts-10x-atj-staging-cloudfoundry-username (tts-10x-atj-staging-cloudfoundry-username): Read complete after 0s [id=/tts-10x-atj-staging/cloudfoundry/username]
tts-10x-atj-staging  data.aws_ssm_parameter.tts-10x-atj-staging-cloudfoundry-password (tts-10x-atj-staging-cloudfoundry-password): Read complete after 0s [id=/tts-10x-atj-staging/cloudfoundry/password]
tts-10x-atj-staging  data.cloudfoundry_domain.tts-10x-atj-staging-doj-demo-data-domain (tts-10x-atj-staging-doj-demo-data-domain): Reading...
                     data.cloudfoundry_space.tts-10x-atj-staging-data-space (tts-10x-atj-staging-data-space): Reading...
tts-10x-atj-staging  data.cloudfoundry_domain.tts-10x-atj-staging-doj-demo-data-domain (tts-10x-atj-staging-doj-demo-data-domain): Read complete after 0s [id=50ba3f69-cd54-4963-9172-14f3334b479e]
tts-10x-atj-staging  data.cloudfoundry_space.tts-10x-atj-staging-data-space (tts-10x-atj-staging-data-space): Read complete after 0s [id=132fc49b-e29e-40b3-8914-4233e4d4caf4]
tts-10x-atj-staging  cloudfoundry_route.tts-10x-atj-staging-doj-demo-route (tts-10x-atj-staging-doj-demo-route): Refreshing state... [id=90846ea2-699e-4416-9037-2c3b739adc90]
tts-10x-atj-staging  cloudfoundry_app.tts-10x-atj-staging-doj-demo_tts-10x-atj-staging-doj-demo-app_736F8430 (tts-10x-atj-staging-doj-demo/tts-10x-atj-staging-doj-demo-app): Refreshing state... [id=828eaa40-786a-45ce-9a44-3271b1e659d5]
tts-10x-atj-staging  No changes. Your infrastructure matches the configuration.
tts-10x-atj-staging  Terraform has compared your real infrastructure against your configuration
                     and found no differences, so no changes are needed.

@danielnaab danielnaab merged commit 056fc5f into main Jun 19, 2024
3 checks passed
@danielnaab danielnaab deleted the docker-static-assets branch June 19, 2024 04:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant